|
![](/i/fill.gif) |
"Warp" <war### [at] tag povray org> wrote:
> I have to go to Thorsten's side in this: I don't really see how
> this is a "real problem".
This is how: I have a lot of my own modifications, and am constantly working
on new ones. For you to understand the degree of those modifications, I
would list some of them here:
- it is a Win32 console executable (running with detached console, i.e. w/o
standard Win32 character console),
- output to hi-color (16-bit) DirectDraw full-screen window,
- own custom console *within* that window,
- own means of synchronization with other Win32 applications (set of Events,
plus a memory-mapped file),
- numerous own patches (representing major modifications to POV-Ray; like,
say, building density maps),
- etc.
Once again, I'm constantly working on that, making my own (sic!) errors in
the process. Common sense (as well as many years of experience) suggests
that I do not turn off warnings, since absolute majority of them are indeed
very helpful in spotting bugs. Just as I said on a number of accations,
compiler writers are not idiots.
And now I have to use Tcl/Tk scripts for my build procedure to sort out
warnings. Tell me, is that OK?
Post a reply to this message
|
![](/i/fill.gif) |